feat: generic vm: initial setup #169
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
buffalojoec
force-pushed
the
feat-generic-vm
branch
from
43ec754 to
d573769
Compare
buffalojoec
changed the title
buffalojoec
changed the title
Collaborator
Author
|
Merging into feature branch! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Makes Mollusk generic over some implementation of a VM. This means you could run Mollusk with Firedancer's VM or a custom Solana-compatible VM.
Simply implement the calling convention for the desired VM and use
Mollusk::<MyVM>::new_with_vm(..).The strategic use of generic parameters with default values means that all existing users should never have to add a type parameter and should get
Mollusk<AgaveVM>by default, which is the exact same harness the library has been using since the beginning.